-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support to filter traces using !~
#2410
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for this. Overall looks great, just have a few small comments.
There are some failing tests. I think they're all related and we need to remove the unsupported cases here :
|
a5ac505
to
3b1c823
Compare
e2e passed on my local, might be some flaky test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for adding doc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with the map[string] implementation as-is. There is no regression on current performance, so let's not hold up this awesome feature. We can follow up with performance improvements as needed.
Sure, then we are good to go 🚀 |
What this PR does:
!~
in tracqlWhich issue(s) this PR fixes:
Fixes #1990
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]